Job processing apparatus, method of controlling job processing apparatus, and storage medium

ABSTRACT

In a case where a job associated with a user has not been successfully stored in a job processing apparatus, it is not possible to exclusively notify the user that the job has not been successfully stored. A control method in a job processing apparatus includes storing a job such that the job is associated with a user, storing, identification information for identifying the user associated with a job that has not been successfully stored, and notifying the user that the job has not been stored according to login to the job processing apparatus, by the user, in a case where identification information for identifying the user having logged in to the job processing apparatus has been stored.

BACKGROUND

1. Field

Aspects of the present invention generally relate to a job processingapparatus that stores a job and executes the stored job, a method ofcontrolling the job processing apparatus, and a storage medium.

2. Description of the Related Art

Conventionally, an image forming apparatus is known which receives aprint job input from a host computer and rasterizes print data of thereceived job to print. In such an image forming apparatus, memory may beexhausted during the rasterization of print data. There is a knowntechnique for notifying an operation panel of the image formingapparatus or the host computer of the exhaustion of the memory (refer toJapanese Patent Application Laid-Open No. 2007-245703).

In a case where a job is not successfully stored, the conventionalmethod can be used for notifying a user that the job has not beensuccessfully stored. However, in a case where a job associated with theuser has not been successfully stored, it is not possible to exclusivelynotify the user that the job has not been successfully stored. Further,by using the conventional method, in a case where a job associated witha user has not been successfully stored, it is not possible to notifythe user of information about the job, which has not been successfullystored, associated with the user, and in a case where a job associatedwith a user has been successfully stored, it is not possible to notifythe user of information about the job, which has been successfullystored, associated with the user.

SUMMARY

According to an aspect of the present invention, a job processingapparatus includes a first storing unit configured to store a job suchthat the job is associated with a user, a second storing unit configuredto store identification information for identifying the user associatedwith a job that has not been successfully stored in the first storingunit, and a notification unit configured to notify the user that the jobhas not been stored according to login to the job processing apparatus,by the user, in a case where identification information for identifyingthe user having logged in to the job processing apparatus has beenstored in the second storing unit.

Further features of the present disclosure will become apparent from thefollowing description of exemplary embodiments with reference to theattached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a functional configuration of amultifunctional peripheral (MFP) according to a present exemplaryembodiment.

FIG. 2 is a cross sectional view illustrating a configuration of the MFPaccording to the present exemplary embodiment.

FIGS. 3A and 3B each illustrate a screen according to a first exemplaryembodiment.

FIG. 4 is a flowchart illustrating a control example according to thefirst exemplary embodiment.

FIGS. 5A and 5B each illustrate an example of a table according to thefirst exemplary embodiment.

FIG. 6 is a flowchart illustrating a control example according to thefirst exemplary embodiment.

FIG. 7 illustrates a screen according to the first exemplary embodiment.

FIGS. 8A and 8B each illustrate a screen according to the firstexemplary embodiment.

FIG. 9 is a flowchart illustrating a control example according to thefirst exemplary embodiment.

FIG. 10 is a flowchart illustrating a control example according to asecond exemplary embodiment.

FIG. 11 illustrates an example of a table according to the secondexemplary embodiment.

FIG. 12 is a flowchart illustrating a control example according to thesecond exemplary embodiment.

FIG. 13 illustrates a screen according to the second exemplaryembodiment.

FIG. 14 is a flowchart illustrating a control example according to athird exemplary embodiment.

FIG. 15 illustrates an example of a table according to the thirdexemplary embodiment.

FIG. 16 is a flowchart illustrating a control example according to thethird exemplary embodiment.

FIG. 17 illustrates a screen according to the third exemplaryembodiment.

DESCRIPTION OF THE EMBODIMENTS

Various exemplary embodiments will be described in detail below withreference to the attached drawings. It is to be understood that theseexemplary embodiments are not seen to be limiting.

The following describes a print system according to a first exemplaryembodiment with reference to FIG. 1.

In the first exemplary embodiment, a job associated with a user isreceived, and the received job is stored. If the received job has notbeen successfully stored, the user is exclusively notified that there isa job that has not been stored.

Details are described below.

The print system according to the present exemplary embodiment includesa multifunctional peripheral (MFP) 100 and a personal computer (PC) 101.The MFP 100 is an example of a print apparatus (also referred to as a“job processing apparatus”). The PC 101 is an external informationprocessing apparatus.

The MFP 100 has an image reading function to read a document to generateimage data. The MFP 100 also has a print function (copy function) toprint an image on a sheet based on the generated image data. The MFP 100also has a print function (PC print function) to receive a print jobfrom an external apparatus such as the PC 101, and to print a text or animage on a sheet based on data for which a print instruction isreceived. The printing to be carried out by the print function may becolor or monochrome printing.

The MFP 100 is connected to the PC 101 via a local area network (LAN)102 to communicate with the PC 101.

In the present exemplary embodiment, the PC 101 inputs a print job tothe MFP 100 via a network such as the LAN 102. Then, the MFP 100processes the print job input from the PC 101 via the network such asthe LAN 102.

While the present exemplary embodiment describes an exemplary case wherethe MFP 100 and the PC 101 are connected each other via the LAN 102, theMFP 100 and the PC 101 may be connected each other via a wide areanetwork (WAN) such as the Internet. Alternatively, the MFP 100 and thePC 101 may be connected each other via a universal serial bus (USB)cable. Further, the MFP 100 and the PC 101 may be configured to becommunicable with each other via wireless communications such aswireless fidelity (Wi-Fi) or Bluetooth®.

The PC 101 generates image data using application software and sends thegenerated image data to the MFP 100. While the present exemplaryembodiment describes the PC 101 as an example of an external informationprocessing apparatus, the information processing apparatus is notlimited to the PC 101 and may be a mobile information terminal such as apersonal digital assistant (PDA) or a smartphone.

The MFP 100 according to the present exemplary embodiment includes acontroller unit (control unit) 110, a reader unit 120, a printer unit130, an external interface (I/F) 140, an operation unit 150, a hard disk(HDD) 160, and a compression/rasterization unit 170. These componentsare arranged on a system bus 117 and electrically connected one anotherto send or receive a control command or data to or from one another.Further, the external I/F 140, which is an example of a communicationunit, is an interface for sending and receiving image data to and fromthe external apparatus. The external apparatus is the PC 101 or, forexample, a facsimile, a network connection device, an external dedicatedapparatus, etc.

The reader unit 120 includes a scanner control unit 121 and a documentsheet feeding unit 122. The scanner control unit 121 controls thecommunication with the controller unit 110. The document sheet feedingunit 122 feeds a document.

A document reading instruction to the reader unit 120 is given from thecontroller unit 110 via the scanner control unit 121, and the readerunit 120 optically reads an image of the document and converts it intoimage data in the form of electric signals. While the present exemplaryembodiment will describe a case where a document reading instruction tothe reader unit 120 is given from the controller unit 110 via thescanner control unit 121, this is not a limiting case. In a case wherethe reader unit 120 of the MFP does not include the scanner control unit121 as its component, a document reading instruction to the reader unit120 may be given directly from a central processing unit (CPU) 111 ofthe controller unit 110.

The printer unit 130 includes a printer control unit 131 configured tocontrol the communication with the controller unit 110. The printer unit130 further includes a sheet feeding unit 132 including a sheet holdingunit (sheet feeding cassette, manual sheet feeding tray, etc.) forstoring sheets to be used in printing. While the present exemplaryembodiment describes multiple sheet feeding cassettes and a manual sheetfeeding tray included in the MFP 100 as an example of the sheet holdingunit 132, the sheet holding unit 132 may be a sheet feeding deckincluded in a sheet feeding apparatus to be connected to the MFP 100.

Further, the printer unit 130 executes print processing of a job to beprinted that is stored in the HDD 160 of the controller unit 110. Animage data print instruction to the printer unit 130 is given from thecontroller unit 110 via the printer control unit 131, and the printerunit 130 forms (prints) an image based on the image data using toner ona sheet fed from the sheet holding unit and then transfers and fixes theimage. While the present exemplary embodiment describes a case where animage data print instruction to the printer unit 130 is given from thecontroller unit 110 via the printer control unit 131, this is not alimiting case. In a case where the printer unit 130 of the MFP does notinclude the printer control unit 131 as its component, an image dataprint instruction to the printer unit 130 may be given directly from theCPU 111 of the controller unit 110.

The controller unit 110 includes therein a non-volatile memory (storageunit) such as the HDD 160 capable of storing multiple jobs to beprocessed. The HDD 160 can store system software, image data compressedby the compression/rasterization unit 170, which will be describedbelow. Further, the HDD 160 can store print data of a print job to beprocessed and bibliographic information extracted by analysis ofattributes of the print job. The bibliographic information refers to,for example, the time and data of the receipt of the job, the storagelocation (IP address, path, job name, etc.) of the received job, andprint setting information (color mode, sheet size, number of copies,finishing, etc.) about the received job.

The HDD 160 can also store authentication information such as a username and a password for logging in to the MFP 100. Further, the HDD 160can store a bibliographic information table 500, which will be describedbelow with reference to FIG. 5A.

While the present exemplary embodiment describes the HDD 160 as anexample of a high-capacity and non-volatile storage apparatus, anyhigh-capacity and non-volatile storage apparatus can be used such as anon-volatile memory, e.g., a solid state drive (SSD).

The controller unit 110 has multiple functions. For example, thecontroller unit 110 can execute a print job by storing in the HDD 160image data of a document read by the reader unit 120, reading the imagedata from the HDD 160, and causing the printer unit 130 to print animage on a sheet based on the image data. Further, the controller unit110 can execute a scanner function by converting image data of adocument read by the reader unit 120 into code data and sending the codedata to the PC 101, which is an external apparatus, via the external I/F140, which is an example of a communication unit. Further, thecontroller unit 110 can execute a print function (PC print function) bystoring in the HDD 160 a print job received from the PC 101 via theexternal I/F 140, converting the code data read from the HDD 160 intoimage data, and causing the printer unit 130 to print an image on asheet based on the image data.

The controller unit 110 includes the CPU 111, a read-only memory (ROM)115, a random-access memory (RAM) 114, a reader I/F 112, and a printerI/F 113.

The CPU 111 controls the processing, operation, and the like of eachunit included in the MFP 100.

The ROM 115 is a read-only memory and stores in advance programs such asboot sequences, font information, etc.

The RAM 114 is a readable/rewritable memory and stores image data sentfrom the reader unit 120 or the external I/F 140, various types ofprograms, setting information, etc. Further, the RAM 114 can store anerror information table 510, which will be described below withreference to FIG. 5B.

The ROM 115 or the HDD 160 stores various types of control programs tobe executed by the CPU 111 that are necessary for executing varioustypes of processing specified in flowcharts described below, etc. Then,the CPU 111 reads a program stored in the ROM 115 or the HDD 160, anddevelops the program in the RAM 114 to execute various types ofoperations according to the present exemplary embodiment.

The ROM 115 or the HDD 160 stores, for example, a display controlprogram for displaying various types of user interface screens(hereinafter “UI screen”) on a display unit of the operation unit 150.UI is the abbreviation for “user interface.” Further, the ROM 115 or theHDD 160 stores, as a program for controlling the operation unit 150, aUI function program for recognizing what a user has input from theoperation unit 150, and for switching to a suitable screen or providinga processing request instruction to the controller unit 110.

Furthermore, the ROM 115 or the HDD 160 stores, for example, a pagedescription language (PDL) function program for causing the CPU 111 tointerpret PDL data received from an external apparatus via the externalI/F 140 to rasterize the PDL data into raster image data (bitmap imagedata), and then causing the controller unit 110 to execute the printfunction.

The controller unit 110 stores (saves) in the HDD 160 a job to beprocessed that is input via various input units such as the reader unit120 or the external I/F 140, and reads the job from the HDD 160 tooutput the job to the printer unit 130 to be printed. The controllerunit 110 also controls the job read from the HDD 160 to send the job tothe external apparatus via the external I/F 140.

The compression/rasterization unit 170 includes an image processingblock configured to perform processing to compress or decompress imagedata or the like stored in the RAM 114 or the HDD 160 using varioustypes of compression methods such as the Joint Bi-level Image ExpertsGroup (JBIG) or the Joint Photographic Experts Group (JPEG), and tostore the image data again in the RAM 114. Image data compressed by thecompression/rasterization unit 170 can be sent to the external apparatusvia the external I/F 140.

The controller unit 110 can receive image data from the externalapparatus via the external I/F 140. At the time of storing in the HDD160 image data received via the external I/F 140, the image data iscompressed by the compression/rasterization unit 170. On the other hand,at the time of printing an image on a sheet based on the image datastored in the HDD 160, the image data is decompressed by thecompression/rasterization unit 170. Further, the controller unit 110executes various types of output processing to output a job to beprocessed that is stored in the HDD 160. While the present exemplaryembodiment describes the exemplary case where jobs are stored in the HDD160, the jobs may be stored in a volatile RAM.

The reader I/F 112 is an interface for connecting to the reader unit120, which is an image input apparatus. The printer I/F 113 is aninterface for connecting to the printer unit 130, which is an imageoutput apparatus. The controller unit 110 synchronously/asynchronouslyconverts or controls image data via the reader I/F 112 or the printerI/F 113.

The MFP 100 includes the operation unit 150 including a display unit,which corresponds to an example of a user interface unit. The operationunit 150 of the MFP 100 according to the present exemplary embodimentincludes a display unit (not illustrated) and hard keys (notillustrated). The display unit includes a liquid crystal display (LCD)and a touch panel sheet including a transparent electrode (capacitancetype may also be used) attached on the LCD. The LCD displays anoperation screen and/or the status of the MFP 100. The operation unit150 has a function to receive various types of user settings via theoperation screen or the hard keys. The operation unit 150 also has afunction to provide information to the user.

A cross sectional view of the reader unit 120 and the printer unit 130illustrated in FIG. 1 is as illustrated in FIG. 2.

The following describes an operation to output an image on a sheet basedon image data transferred to the printer unit 130.

Image data transferred to the printer unit 130 is converted by a laserunit 222 into a laser beam corresponding to the image data. Then,photosensitive drums 223 to 226 are irradiated with the laser beam toform on the photosensitive drums 223 to 226 latent images correspondingto the laser beam. Toner is applied to the latent image portions of thephotosensitive drums 223 to 226 by development units 227 to 230. A colorprinter includes four photosensitive drums and four development unitsfor cyan, yellow, magenta, and black.

The printer unit 130 includes sheet feeding cassettes 251 to 254 and amanual sheet feeding tray 250 as sheet holding units included in thesheet holding unit 132. Each of the sheet feeding cassettes 251 to 254is in the shape of a drawer. Each of the sheet feeding cassettes 251 to254 and the manual sheet feeding tray 250 can hold multiple sheets. Theprinter unit 130 may include multiple sheet feeding cassettes and manualsheet feeding trays, or may include at least one of a sheet feedingcassette and a manual sheet feeding tray. The present exemplaryembodiment will describe the MFP 100 including four sheet feedingcassettes and one manual sheet feeding tray.

In the printer unit 130, a sheet is fed from one of the sheet feedingcassettes 251 to 254 and the manual sheet feeding tray 250, and thetoner applied to the photosensitive drums 223 to 226 is transferred ontothe sheet. Thereafter, the sheet is conveyed to a fixing unit 233 to fixthe toner onto the sheet by heat and pressure. The temperature of thefixing unit and the sheet transfer speed are controlled based onattribute information such as the grammage of a sheet stored in the HDD160 as setting values of the sheet holding units configured to feedsheets. The sheet having passed through the fixing unit 233 isdischarged to a sheet output tray 236 by conveying rollers 234 and 235.

In the MFP that does not include the sheet output tray 236 as a sheetoutput unit, the sheet having passed through the fixing unit 233 may bedischarged within its body part being a sheet output unit.

While the present exemplary embodiment describes a case where the colorprinter including four photosensitive drums and four development unitsis used, in another embodiment, a monochrome printer including onephotosensitive drum and one development unit can be used. Further, whilethe present exemplary embodiment describes the electrophotographicmethod of printing an image on a sheet, an inkjet method or any othermethod by which an image can be printed may be used.

In the present exemplary embodiment, a print job is input from the PC101 to the MFP 100 using a print function of an arbitrary application, aprinter driver, etc.

For example, the user can designate the MFP 100 (a printer name 301) tobe used to execute a print job on a printer driver screen 300, which isillustrated in FIG. 3A, displayed on an operation unit (not illustrated)of the PC 101. Further, the user can designate, for example, a colormode, sheet size, number of copies, finishing, etc. as a print setting302. Further, the user can designate as an output mode 303 of a printjob, for example, “print,” “secure print,” “encrypted secure print,”“save,” “hold,” etc.

In a case where, for example, “print” is designated as the output mode303, print data such as PDL data reflecting the print setting 302designated by a printing style designation function provided by theprinter driver is generated. Then, a print job associated with userinformation (e.g., login name of the PC 101, authenticated useridentification (ID), etc.) is sent to the MFP 100 designated by theuser. Examples of the user information to be associated with the printjob are the login name of the PC 101 and the authenticated user ID.Alternatively, a confirmation window 310 illustrated in FIG. 3B may bedisplayed on the operation unit (not illustrated) of the PC 101 at thepress of an OK button 304 on the printer driver screen 300 in FIG. 3A bythe user. In this case, a user name 311 input by the user on theconfirmation window 310 may be associated with the print job. Then, theMFP 100 receives the print job associated with the user information, andexecutes printing.

In the case where, for example, “save” or “hold” is designated as theoutput mode 303, print data such as PDL data reflecting the printsetting 302 is generated. Then, the print job associated with the userinformation is sent to the MFP 100 designated by the user. Thereafter,the MFP 100 receives the print job associated with the user information,and stores the received print job in the HDD 160.

In the case where, for example, “secure print” is designated as theoutput mode 303, for example, the confirmation window 310 illustrated inFIG. 3B prompts the user to input the user name 311 and a password 312.Then, print data such as PDL data reflecting the print setting 302 isgenerated. Thereafter, the print job associated with the userinformation including the password is sent to the MFP 100 designated bythe user. Then, the MFP 100 receives the print job associated with theuser information including the password, and stores the received printjob in the HDD 160.

In the case where, for example, “encrypted secure print” is designatedas the output mode 303, for example, the confirmation window 310illustrated in FIG. 3B prompts the user to input the user name 311 andthe password 312. Then, print data such as PDL data reflecting the printsetting 302 is generated. Thereafter, the print data is encrypted, andthe print job associated with the user information including thepassword is sent to the MFP 100 designated by the user. Then, the MFP100 receives the print job associated with the user informationincluding the password, and stores the received print job in the HDD160.

The following describes in detail a process for storing in the HDD 160bibliographic information and print data of a received job in the MFP100 according to the present exemplary embodiment with reference to theflowchart illustrated in FIG. 4. The CPU 111 of the controller unit 110executes a PDL function program read from the ROM 115 or the HDD 160 anddeveloped in the RAM 114 to carry out the process.

In step S401, the CPU 111 determines whether a job has been received viathe external I/F 140. A job to be received in step S401 is, for example,a job input from the PC 101 to the MFP 100 via the printer driver screen300 illustrated in FIG. 3A described above. As a result of thedetermination in step S401, if the CPU 111 determines that a job hasbeen received (YES in step S401), the processing proceeds to step S402.On the other hand, step S401 is repeated until a job has been received.

In step S402, the CPU 111 determines whether a forcible reservationsetting of the MFP 100 having received the job in step S401 is on.Whether to set the forcible reservation setting on or off can bedetermined arbitrarily for each MFP 100 by the user (administrator). Theforcible reservation refers to forcible storage of a received print jobin the HDD 160 in a case where the print job associated with userinformation is received. Specifically, in a case where the forciblereservation setting is on, even if, for example, “print” is designatedas the output mode 303 of the printer driver, a job input to the MFP 100is forcibly stored in the HDD 160.

As a result of the determination in step S402, if the CPU 111 determinesthat the forcible reservation setting is on (YES in step S402), theprocessing proceeds to step S403. On the other hand, in step S402, ifthe CPU 111 determines that the forcible reservation setting is not on(NO in step S402), the processing proceeds to step S410.

In step S403, the CPU 111 analyzes the setting of the job received instep S401, and determines whether the job is a forcible reservationtarget (i.e., whether the job is to be forcibly stored in the HDD 160).For example, in a case where information about the user having input thejob is not specified (not set), even if the forcible reservation settingof the MFP 100 having received the job is on, the job may be excludedfrom the forcible reservation target. Further, for example, in a casewhere information about the user having input the job indicates aspecific user, even if the forcible reservation setting of the MFP 100having received the job is on, the job may be excluded from the forciblereservation target. Furthermore, for example, in a case where an IPaddress of a job input source is a specific IP address, even if theforcible reservation setting of the MFP 100 having received the job ison, the job may be excluded from the forcible reservation target.Various types of conditions for setting a job as a forcible reservationtarget may be configured to be arbitrarily settable by the user(administrator).

As a result of the determination in step S403, if the CPU 111 determinesthat the job is a forcible reservation target (YES in step S403), theprocessing proceeds to step S404. On the other hand, in step S403, ifthe CPU 111 determines that the job is not a forcible reservation target(NO in step S403), the processing proceeds to step S410.

In step S404, the CPU 111 analyzes an attribute of the received job, anddetermines whether bibliographic information has been successfullyextracted therefrom.

The bibliographic information refers to, for example, a date/time 501 ofthe receipt of the job, a storage location 502 (IP address, path, jobname, etc.) of the received job, and a print setting 503 (color mode,sheet size, number of copies, finishing, etc.) of the received job.

There may be a case where multiple MFPs 100 are communicably connectedvia a network such as the LAN 102. In this case, the MFP 100 for storingprint data of the received job (the MFP 100 will be referred to as a“storage apparatus”), the MFP 100 for registering (storing) thebibliographic information (the MFP 100 will be referred to as a“bibliography server apparatus”), and the MFP 100 for executing the job(the MFP 100 will be referred to as an “output apparatus”) may bedifferent from one another. Thus, the storage location (IP address andpath) of the received job is managed in the bibliographic information.

As a result of the determination in step S404, if the CPU 111 determinesthat the bibliographic information has been successfully extracted (YESin step S404), the processing proceeds to step S405. On the other hand,if the CPU 111 determines that the bibliographic information has notbeen successfully extracted (NO in step S404), the process illustratedin FIG. 4 ends. A case where the bibliographic information has not beensuccessfully extracted is a case where, for example, a job for which nouser information has been set is input and, therefore, an attribute ofthe job cannot be analyzed. When the CPU 111 determines in step S404that the bibliographic information has not been successfully extracted,the process illustrated in FIG. 4 may end after notification of theunsuccessful extraction of the bibliographic information is made to theuser.

In step S405, the CPU 111 stores in the HDD 160 print data extractedfrom the job received in step S401, and then the processing proceeds tostep S406. The print data is PDL data or the like generated byreflecting the print setting 302 designated by the printing styledesignation function provided by the printer driver.

In step S406, the CPU 111 determines whether the print data has beensuccessfully stored in the HDD 160. As a result of the determination instep S406, if the CPU 111 determines that the print data has beensuccessfully stored in the HDD 160 (YES in step S406), the processingproceeds to step S407. On the other hand, in step S406, if the CPU 111determines that the print data has not been successfully stored in theHDD 160 (NO in step S406), the processing proceeds to step S409.Examples of a case where print data has not been successful storedinclude a case where the free space of the HDD 160 is not enough tostore the print data, a case where the file size of print data to bestored in the HDD 160 exceeds the file size of print data that can bestored in the HDD 160, and a case where the number of jobs to be storedin the HDD 160 exceeds the upper limit of the number of jobs that can bestored in the HDD 160 per user.

In step S407, the CPU 111 stores in the HDD 160 the bibliographicinformation extracted from the job received in step S401, and then theprocessing proceeds to step S408.

In step S408, the CPU 111 determines whether the bibliographicinformation has been successfully stored in the HDD 160. As indicated bythe bibliographic information table 500 in FIG. 5A, the bibliographicinformation stored in the HDD 160 is managed for each user having inputthe job based on a user name 504. In the example of the bibliographicinformation table 500 in FIG. 5A, bibliographic information for UserA,bibliographic information for UserB, and bibliographic information forUserC are managed. For example, the bibliographic information table 500indicates that a job (job name: “AAA.ppt”) input to the MFP 100 by UserAwas received on “Apr. 10, 2012, 10:34:45.” Further, as to the storagelocation of the job, the bibliographic information table 500 indicatesthat the IP address is “192.168.2.11” and the path is“/printdata/0015/xxx.” Furthermore, the bibliographic information table500 indicates that the print settings of the job are A3, full color,staple finishing (upper left), and 100 copies to be printed.

As a result of the determination in step S408, if the CPU 111 determinesthat the bibliographic information has been successfully stored (YES instep S408), it is considered that the received job has been successfullystored in the HDD 160. Then, the process illustrated in FIG. 4 ends. Onthe other hand, in step S408, if the CPU 111 determines that thebibliographic information has not been successfully stored (NO in stepS408), the processing proceeds to step S409. A case where thebibliographic information has not been successfully stored is, forexample, a case where the free space of the HDD 160 is not enough tostore the bibliographic information.

In step S409, the CPU 111 registers the user information associated withthe job received in step S401 in the error information table 510, whichis illustrated in FIG. 5B, stored in the RAM 114. The error informationtable 510 stored in the RAM 114 manages information about the user (auser name 511) having input the job that has not been successfullystored in the HDD 160. The error information table 510 illustrated inFIG. 5B as an example indicates that a job input by UserA and a jobinput by UserC have not been successfully stored. The processillustrated in FIG. 4 ends after the process of step S409.

In step S410, the CPU 111 determines whether the output mode of the jobreceived in step S401 is “print.” The output mode of a job is determinedby the output mode 303 designated by the printer driver. As a result ofthe determination in step S410, if the CPU 111 determines that theoutput mode is “print” (YES in step S410), the processing proceeds tostep S411. On the other hand, in step S410, if the CPU 111 determinesthat the output mode is not “print” (NO in step S410), the processingproceeds to step S412. Cases where the CPU 111 determines in step S410that the output mode is not “print” are cases where, for example “secureprint,” “encrypted secure print,” “store,” “hold,” etc. is designated asthe output mode of the job received in step S401.

In step S411, the CPU 111 requests execution of the job received in stepS401, and executes printing based on the print setting 302 (e.g., colormode, sheet size, number of copies, finishing, etc.) designated by theprinter driver. At the time of the execution of printing, the printerunit 130 controls the temperature of the fixing unit and the sheettransfer speed based on the attribute information such as the sheetgrammage stored in the HDD 160 as the setting values of the sheetholding unit. The process illustrated in FIG. 4 ends after the processof step S411.

In step S412, the CPU 111 requests execution of the job received in stepS401, and stores the job in the HDD 160. The process illustrated in FIG.4 ends after the process of step S412.

The foregoing describes in detail the process for storing bibliographicinformation and print data of the received job in the HDD 160 in the MFP100 according to the first exemplary embodiment.

While the foregoing describes the case where the received job isforcibly stored in the HDD 160 in the case where the forciblereservation setting of the MFP 100 having received the job is set on,this is not a limiting case. For example, there may be a case where ajob can be input to the MFP 100 with the “forcible reservation setting”designated as the output mode 303 of the printer driver. In this case,the received job may be forcibly stored in the HDD 160 even if theforcible reservation setting of the MFP 100 having received the job isoff.

The following describes in detail a process for displaying a job list ofan authenticated user in the MFP 100 according to the first exemplaryembodiment with reference to the flowchart illustrated in FIG. 6. TheCPU 111 of the controller unit 110 executes a UI function program readfrom the ROM 115 or the HDD 160 and developed in the RAM 114 to carryout the process. As indicated by a job list screen 800 in FIG. 8A, thejob list shows bibliographic information about the jobs stored in theHDD 160 that is displayed on the operation unit 150. The user can selectan arbitrary job from the job list screen 800 illustrated in FIG. 8A,and gives an instruction to execute the selected job.

In step S601, the CPU 111 displays on the operation unit 150 anauthentication screen 700, which is illustrated in FIG. 7, for loggingin to the MFP 100, and then the processing proceeds to step S602.

In step S602, the CPU 111 determines whether the user inputspredetermined user information (e.g., a user name 701 and a password702), and presses a login button 703 on the authentication screen 700.If the CPU 111 determines that the login button 703 is pressed (YES instep S602), the processing proceeds to step S603. Step S602 is repeateduntil the login button 703 is pressed.

In step S603, the CPU 111 executes authentication by collatingauthentication information such as the user name and the password storedin the HDD 160 based on the user information input on the authenticationscreen 700 by the user, and then the processing proceeds to step S604.

In step S604, the CPU 111 determines whether the authentication executedin step S603 is successful. If the CPU 111 determines that theauthentication is successful (YES in step S604), the processing proceedsto step S606. On the other hand, in step S604, if the CPU 111 determinesthat the authentication is not successful (NO in step S604), theprocessing proceeds to step S605.

In step S605, the CPU 111 notifies the user of the authenticationfailure, and the processing returns to step S602.

In step S606, the CPU 111 refers to the bibliographic information table500, which is illustrated in FIG. 5A, stored in the HDD 160, and theprocessing proceeds to step S607. At the time of referring to thebibliographic information table 500, the user name 701 of theauthenticated user is searched for using as a key the user name 504registered in the bibliographic information table 500. As a result ofthe search, the user name 504 and the user name 701 are compared, andonly the bibliographic information about the authenticated user isreferred to.

In step S607, the CPU 111 acquires the bibliographic information aboutthe authenticated user based on the result referred to in step S606, andthe processing proceeds to step S608. In the bibliographic informationtable 500 illustrated in FIG. 5 as an example, in a case where the username 701 of the authenticated user is “UserA,” only the bibliographicinformation with the user name 504 of “UserA” is acquired among all thebibliographic information registered in the bibliographic informationtable 500.

In step S608, the CPU 111 refers to the error information table 510stored in the RAM 114, and the processing proceeds to step S609. At thetime of referring to the error information table 510, the user name 701of the authenticated user is searched for using as a key the user name511 registered in the error information table 510.

In step S609, the CPU 111 determines whether information (user name)about the authenticated user is registered in the error informationtable 510 based on the result referred to in step S608. As a result ofthe determination in step S609, if the CPU 111 determines that theinformation is registered (YES in step S609), the processing proceeds tostep S611. On the other hand, in step S609, if the CPU 111 determinesthat the information is not registered (NO in step S609), the processingproceeds to step S610.

In step S610, the CPU 111 displays on the operation unit 150 (job list)the bibliographic information (i.e., the bibliographic information aboutthe authenticated user) acquired in step S607. For example, as indicatedin the job list screen 800 in FIG. 8A, the bibliographic informationabout each job input to the MFP 100 by the authenticated user (UserA)and successfully stored in the HDD 160 is displayed on the job list. Theprocess illustrated in FIG. 6 ends after the process of step S610.

In step S611, the CPU 111 displays on the operation unit 150 (job list)the bibliographic information (i.e., the bibliographic information aboutthe authenticated user) acquired in step S607 and the error informationabout the authenticated user. For example, as indicated by a job listscreen 810 in FIG. 8B, the bibliographic information about each jobinput to the MFP 100 by the authenticated user (UserA) and successfullystored in the HDD 160 is displayed on the job list. Further, a message803 to notify the user of storage error information relating to theauthenticated user (i.e., there is a job that was input to the MFP 100by the authenticated user and was not successfully stored at the time ofreceipt) is displayed on the job list screen 810 illustrated in FIG. 8B.The process illustrated in FIG. 6 ends after the process of step S611.

The foregoing describes in detail the process for displaying the joblist of the authenticated user on the MFP 100 according to the firstexemplary embodiment.

While the foregoing describes the case where the authentication forlogging in to the MFP 100 is executed based on the user informationinput by the user on the authentication screen 700 illustrated in FIG. 7in steps S601 to S604, this is not a limiting case. The authenticationmay be executed at the time of logging in to the MFP 100 by reading theuser information such as the user ID and the password registered inadvance on an integrated circuit (IC) card.

While FIG. 8B illustrates the exemplary case where the message 803 isdisplayed on the job list screen 810 illustrated in FIG. 8B to notifythe user of the storage error information about the authenticated userin step S611, this is not a limiting case. The notification of thestorage error information about the authenticated user may be providedin any other form from which the user can easily recognize that there isa job that was input by the authenticated user and was not successfullystored at the time of receipt. For example, a pop-up screen (notillustrated) may be displayed on the operation unit 150 to notify theuser of the storage error information about the authenticated user.Alternatively, other identifiable marks, sound, or light may be used tonotify the user of the storage error information about the authenticateduser. Further, a notification of detailed information (e.g., job name,date/time of job receipt, reason of unsuccessful storage of the job,etc.) about the job that was not successfully stored at the time ofreceipt may also be provided on the job list screen 810 illustrated inFIG. 8B as the storage error information about the authenticated user.

The following describes in detail a process for executing a job storedin the HDD 160 in the MFP 100 according to the first exemplaryembodiment. The CPU 111 of the controller unit 110 executes a PDLfunction program read from the ROM 115 or the HDD 160 and developed inthe RAM 114 to carry out the process. The process starts with the joblist being displayed on the operation unit 150.

In step S901, the CPU 111 determines whether an instruction to execute ajob stored in the HDD 160 has been received. For example, when the userselects arbitrary bibliographic information from the list ofbibliographic information about each job displayed on the job listscreen 810 in FIG. 8B and presses a print start button 802, aninstruction to execute the job can be received. As a result of thedetermination in step S901, if the CPU 111 determines that a jobexecution instruction has been received (YES in step S901), theprocessing proceeds to step S902. Step S901 is repeated until a jobexecution instruction has been received.

In step S902, the CPU 111 analyzes the bibliographic information aboutthe job for which the job execution instruction has been received instep S901, and then the processing proceeds to step S903.

In step S903, the CPU 111 acquires from the HDD 160 print data of thejob for which the job execution instruction has been received in stepS901, and then the processing proceeds to step S904.

In step S904, the CPU 111 executes the job for which the job executioninstruction has been received in step S901 based on the bibliographicinformation (e.g., print setting information) analyzed in step S902 andthe print data acquired in step S903, and then the processing proceedsto step S905.

In step S905, the CPU 111 refers to the error information table 510stored in the RAM 114, and then the processing proceeds to step S906. Atthe time of referring to the error information table 510, the user name701 of the authenticated user is searched for using as a key the username 511 registered in the error information table 510.

In step S906, the CPU 111 determines whether information (user name)about the authentication user is registered in the error informationtable 510 based on the result referred to in step S905. As a result ofthe determination in step S906, if the CPU 111 determines that theinformation is registered (YES in step S906), the processing proceeds tostep S907. On the other hand, in step S906, if the CPU 111 determinesthat the information is not registered (NO in step S906), the processillustrated in FIG. 9 ends.

In step S907, the CPU 111 deletes the information (user name) about theauthenticated user among all the user information (user name) registeredin the error information table 510. For example, in a case where theuser name of the authenticated user is “UserA,” “UserA” registered inthe error information table 510 is deleted. The message 803 of the errorinformation displayed on the job list screen 800 in FIG. 8B may bedeleted according to the deletion of the error information about theauthenticated user from the error information table 510. The processillustrated in FIG. 9 ends after the process of step S907.

The foregoing describes details of the process for executing the jobstored in the HDD 160 in the MFP 100 according to the first exemplaryembodiment.

While the foregoing describes the case where the error information aboutthe authenticated user is deleted from the error information table 510when the job stored in the HDD 160 is executed following the receipt ofthe instruction to execute the job, this is not a limiting case. Forexample, the error information about the authenticated user may bedeleted from the error information table 510 when arbitrarybibliographic information is selected among all the bibliographicinformation of the jobs displayed on the job list screen 810 in FIG. 8B.Alternatively, the error information about the authenticated user may bedeleted from the error information table 510 when a predetermined timehas elapsed since the display of the message 803 of the storage errorinformation on the job list screen 810 in FIG. 8B was performed.Alternatively, the CPU 111 may delete the error information about theauthenticated user from the error information table 510 when the userlogs out from the MFP 100. Specifically, it is also possible to arrangesuch that the message 803 of the error information about theauthenticated user is not displayed on the job list screen 810 in FIG.8B when the authenticated user logs in to the MFP 100 again afterlogging out from the MFP 100.

As described above, according to the first exemplary embodiment, in thecase where a job associated with user information has been received andthe received job has not been successfully stored, the user informationis registered in the error information table 510. Then, when the user isauthenticated, the user is notified that there is a job that was notsuccessfully stored among the jobs input by the authenticated user. Inthis way, jobs input by other users are excluded from consideration, andthe authenticated user can check whether there is a job that was notsuccessfully stored only among the jobs input by the authenticated user.This significantly improves user convenience.

In the first exemplary embodiment described above, the case whereauthentication for logging in to the MFP 100 has been considered. Thecase described above is as follows. When a job associated with userinformation has been received and the received job has not beensuccessfully stored, the user information is registered in the errorinformation table 510 stored in the RAM 114. Then, when the user isauthenticated, the user is notified that there is a job that was notsuccessfully stored among the jobs input by the authenticated user.

In a second exemplary embodiment, a case where authentication forlogging in to the MFP 100 is not executed will be considered. In a casewhere a job associated with user information has been received and thereceived job has not been successfully stored, the CPU 111 registersstorage unsuccessful information in a bibliographic information table(FIG. 11) stored in the HDD 160. On the other hand, in a case where thereceived job has been successfully stored, the CPU 111 registers storagesuccessful information in the bibliographic information table. Then,when the job list is displayed, the user is notified of the job that hasnot been successfully stored and the job that has been successfullystored such that each of the jobs is associated with user information.This case will be described below as the second exemplary embodiment.

The MFP 100 according to the second exemplary embodiment isdifferentiated from a part of the processes of the first exemplaryembodiment (FIG. 4) for storing bibliographic information and print dataof a received job in the HDD 160. The following mainly describes stepsthat are different from those in the first exemplary embodiment, withreference to FIG. 10. Steps that are similar to those in the firstexemplary embodiment are given the same step numbers, and description ofthe steps is omitted. In the second exemplary embodiment, as indicatedin a bibliographic information table 1100 illustrated in FIG. 11, a username (information) 1101 and a storage result 1102 are also registered inaddition to the date/time 501, the storage location 502, and the printsetting 503 as bibliographic information. The storage result 1102 refersto information about whether a received job has been successfully storedin the HDD 160.

As illustrated in FIG. 10, in step S403, if the CPU 111 determines thatthe job received in step S401 is a forcible reservation target (YES instep S403), the processing proceeds to step S1001.

In step S1001, the CPU 111 analyzes an attribute of the received job anddetermines whether the bibliographic information has been successfullyextracted. The process of step S1001 corresponds to that of step S404 inFIG. 4 described in the first exemplary embodiment. As a result of thedetermination in step S1001, if the CPU 111 determines that thebibliographic information has been successfully extracted (YES in stepS1001), the processing proceeds to step S1002. On the other hand, instep S1001, if the CPU 111 determines that the bibliographic informationhas not been successfully extracted (NO in step S1001), the processillustrated in FIG. 10 ends. When the CPU 111 determines that thebibliographic information has not been successfully extracted, theprocess illustrated in FIG. 10 may end after notification of theunsuccessful extraction of the bibliographic information is made to theuser.

In step S1002, the CPU 111 stores in the HDD 160 the bibliographicinformation extracted from the job received in step S401, and then theprocessing proceeds to step S1003. The process of step S1002 correspondsto that of the step S407 in FIG. 4 described above in the firstexemplary embodiment.

In step S1003, the CPU 111 determines whether the bibliographicinformation has been successfully stored in the HDD 160. The process ofstep S1003 corresponds to that of step S408 in FIG. 4 described above inthe first exemplary embodiment. As a result of the determination in stepS1003, if the CPU 111 determines that the bibliographic information hasbeen successfully stored (YES in step S1003), the processing proceeds tostep S1004. On the other hand, in step S1003, if the CPU 111 determinesthat the bibliographic information has not been successfully stored (NOin step S1003), the process illustrated in FIG. 10 ends. When the CPU111 determines in step S1003 that the bibliographic information has notbeen successfully stored, the process illustrated in FIG. 10 may endafter notification of the unsuccessful storage of the bibliographicinformation is made to the user.

In step S1004, the CPU 111 stores in the HDD 160 print data extractedfrom the job received in step S401, and then the processing proceeds tostep S1005. The process of step S1004 corresponds to that of step S405in FIG. 4 described above in the first exemplary embodiment.

In step S1005, the CPU 111 determines whether the print data has beensuccessfully stored in the HDD 160. The process of step S1005corresponds to that of step S406 in FIG. 4 described above in the firstexemplary embodiment. As a result of the determination in step S1005, ifthe CPU 111 determines that the print data has been successfully stored(YES in step S1005), the processing proceeds to step S1006. On the otherhand, in step S1005, if the CPU 111 determines that the print data hasnot been successfully stored (NO in step S1005), the processing proceedsto step S1007.

In step S1006, storage successful information (OK) is registered in thebibliographic information table 1100 stored in the HDD 160. The “storagesuccessful” indicates that the received job has been successfully storedin the HDD 160. For example, as indicated in the bibliographicinformation table 1100 in FIG. 11, OK (storage successful) is registeredas the storage result 1102 of the job (job name: DDD.txt) input byUserB. The process illustrated in FIG. 10 ends after the process of stepS1006.

In step S1007, storage unsuccessful information (NG) is registered inthe bibliographic information table 1100 stored in the HDD 160. The“storage unsuccessful” indicates that the received job has not beensuccessfully stored in the HDD 160. For example, as indicated in thebibliographic information table 1100 in FIG. 11, NG (storageunsuccessful) is registered as the storage result 1102 of the job (jobname: EEE.jpg) input by UserC. The process illustrated in FIG. 10 endsafter the process of step S1007.

The foregoing describes in detail the steps different from those in thefirst exemplary embodiment among the steps included in the process forstoring bibliographic information and print data of a received job inthe HDD 160 in the MFP 100 according to the second exemplary embodiment.

The following describes in detail a process for displaying a job list inthe MFP 100 according to the second exemplary embodiment with referenceto the flowchart illustrated in FIG. 12. The CPU 111 of the controllerunit 110 executes a UI function program read from the ROM 115 or the HDD160 and developed in the RAM 114 to carry out the process.Authentication for logging in to the MFP 100 is not executed in the MFP100 according to the second exemplary embodiment described below. In thejob list in the second exemplary embodiment, jobs for whichbibliographic information has been successfully stored are listed suchthat a storage result 1302 of each of the jobs (print data) isassociated with a user name (information) 1301, as indicated in a joblist screen 1300 illustrated in FIG. 13. The job list screen 1300illustrated in FIG. 13 is displayed on the operation unit 150.

In step S1201, the CPU 111 determines whether a job list displayinstruction has been received. The job list screen 1300 illustrated inFIG. 13 is invoked, for example, at the press of a button (notillustrated) displayed on the operation unit 150 by the user. As aresult of the determination in step S1201, if the CPU 111 determinesthat a display instruction has been received (YES in step S1201), theprocessing proceeds to step S1202. Step S1201 is repeated until adisplay instruction has been received.

In step S1202, the CPU 111 refers to the bibliographic information table1100, which is illustrated in FIG. 11, stored in the HDD 160 andacquires all the bibliographic information, and then the processingproceeds to step S1203. In step S1202, the user name 1101 and thestorage result 1102 are acquired in addition to the date/time 501, thestorage location 502, and the print setting 503 as bibliographicinformation.

In step S1203, the CPU 111 displays on the operation unit 150 (job list)the bibliographic information acquired in step S1202. For example, asindicated in the job list screen 1300 in FIG. 13, the storage result1302 of the job input to the MFP 100 by UserA and given the job name“AAA.ppt” is “unsuccessful” (NG). On the other hand, the storage result1302 of the job input to the MFP 100 by UserA and given the job name“BBB.txt” is “successful” (OK). Thus, the user can select a job with thestorage result 1302 that is “successful” (OK), and give an instructionto execute the job. With regard to a job with the storage result 1302that is “unsuccessful” (NG), the user may change the settings of the joband the like, and then input the job again from the PC 101 to the MFP100. The process illustrated in FIG. 12 ends after the process of stepS1203.

The foregoing describes in detail the process for displaying the joblist on the MFP 100 according to the second exemplary embodiment. Whilethe foregoing describes the exemplary case where “OK” is displayed toindicate that the received job has been successfully stored and “NG” isdisplayed to indicate that the received job has not been successfullystored on the job list screen 1300 in FIG. 13, this is not a limitingcase. For example, a pop-up screen (not illustrated) from which the usercan easily understand that the job has been successfully stored or notsuccessfully stored may be displayed on the job list screen 1300 tonotify the user of the storage result. Alternatively, other identifiablemarks, sound, or light may be used to notify the user of the storageresult. Further, a notification of detailed information (e.g., reason ofunsuccessful storage of the job, etc.) about the job that was notsuccessfully stored at the time of receipt may also be provided as thestorage result.

As described above, in the second exemplary embodiment, the storageunsuccessful information (NG) is registered in the bibliographicinformation table 1100 in the case where a job associated with userinformation has been received and the received job has not beensuccessfully stored. On the other hand, the storage successfulinformation (OK) is registered in the bibliographic information table1100 in the case where the received job has been successfully stored.

Then, when the job list is displayed, the user is notified of the jobthat was not successfully stored and the job that was successfullystored such that each of the jobs is associated with user information.In this way, the user can easily recognize the jobs that were notsuccessfully stored and the jobs that were successfully stored, amongthe jobs input by the user. This significantly improves userconvenience.

In a third exemplary embodiment, a case where authentication for loggingin to the MFP 100 is not executed will be considered. In a case where ajob associated with user information has been received and the receivedjob has not been successfully stored, storage unsuccessful informationis registered in a job history table (FIG. 15) stored in the HDD 160. Onthe other hand, in a case where the received job has been successfullystored, storage successful information is registered in the job historytable. Then, when the job history is displayed, the user is notified ofthe job that was not successfully stored and the job that wassuccessfully stored such that each of the jobs is associated with userinformation. This case will be described below as the third exemplaryembodiment.

As indicated in a job history table 1500 in FIG. 15, the job historyinformation manages, for example, a date/time 1501 of receipt, a type1503, and a job name 1504 of a received job as history information aboutthe job from which bibliographic information has been successfullyextracted. Further, a department ID 1502 of the user having input thejob, a user name (information) 1505 about the user having input the job,and a storage result 1506 of the received job are managed. The jobhistory table 1500 illustrated in FIG. 15 is stored in the HDD 160.

The difference between the MFP 100 according to the third exemplaryembodiment and the first exemplary embodiment (FIG. 4) is a part of theprocesses for storing bibliographic information and print data of areceived job in the HDD 160. The following mainly describes steps thatare different from those in the first exemplary embodiment, withreference to FIG. 14. Steps that are similar to those in the first andsecond exemplary embodiments are given the same step numbers, anddescription of the steps is omitted.

As illustrated in FIG. 14, in step S406, if the CPU 111 determines thatthe print data extracted from the job received in step S401 has not beensuccessfully stored (NO in step S406), the processing proceeds to stepS1402.

As illustrated in FIG. 14, in step S408, if the CPU 111 determines thatthe print data extracted from the job received in step S401 has beensuccessfully stored (YES in step S408), the processing proceeds to stepS1401. On the other hand, in step S408, if the CPU 111 determines thatthe print data extracted from the job received in step S401 has not beensuccessfully stored (NO in step S408), the processing proceeds to stepS1402.

In step S1401, the storage successful information (OK) is registered inthe job history table 1500 stored in the HDD 160. The “storagesuccessful” indicates that the received job has been successfully storedin the HDD 160. For example, as indicated in the job history table 1500in FIG. 15, OK (storage successful) is registered as the storage result1506 of the job (job name: DDD.txt) input by UserB. The processillustrated in FIG. 14 ends after the process of step S1401.

In step S1402, storage unsuccessful information (NG) is registered inthe job history table 1500 stored in the HDD 160. The “storageunsuccessful” indicates that the received job has not been successfullystored in the HDD 160. For example, as indicated in the job historytable 1500 in FIG. 15, NG (storage unsuccessful) is registered as thestorage result 1506 of the job (job name: EEE.jpg) input by UserC. Theprocess illustrated in FIG. 14 ends after the process of step S1402. Theforegoing describes in detail the steps different from those in thefirst exemplary embodiment among the steps included in the process forstoring bibliographic information and print data of a received job inthe HDD 160 in the MFP 100 according to the third exemplary embodiment.

The following describes in detail a process for displaying the jobhistory on the MFP 100 according to the third exemplary embodiment, withreference to the flowchart illustrated in FIG. 16. The CPU 111 of thecontroller unit 110 executes a UI function program read from the ROM 115or the HDD 160 and developed in the RAM 114 to carry out the process.Authentication for logging in to the MFP 100 is not executed in the MFP100 according to the third exemplary embodiment described below. In thejob history in the third exemplary embodiment, a list of historyinformation (e.g., print history information, storage historyinformation) about the jobs from which the bibliographic information hasbeen successfully extracted is displayed such that the historyinformation is associated with a user name (information) 1701, asindicated in a job history screen 1700 in FIG. 17. The job historyscreen 1700 illustrated in FIG. 17 is displayed on the operation unit150.

In step S1601, the CPU 111 determines whether a job history displayinstruction has been received. The job history screen 1700 illustratedin FIG. 17 is invoked, for example, at the press of a button (notillustrated) displayed on the operation unit 150 by the user. As aresult of the determination in step S1601, if the CPU 111 determinesthat a display instruction has been received (YES in step S1601), theprocessing proceeds to step S1602. Step S1601 is repeated until adisplay instruction has been received.

In step S1602, the CPU 111 refers to the job history table 1500, whichis illustrated in FIG. 15, stored in the HDD 160 and acquires all thehistory information, and then the processing proceeds to step S1603. Instep S1602, the user name 1505 and the storage result 1506 are acquiredin addition to the date/time 1501, the department ID 1502, the type1503, and the job name 1504 as the history information.

In step S1603, the CPU 111 displays on the operation unit 150 (jobhistory) the history information acquired in step S1602. For example, asindicated in the job history screen 1700 in FIG. 17, a (storage) result1702 of the job input by UserA and given the job name “AAA.ppt” is“unsuccessful” (NG). On the other hand, the storage result 1702 of thejob input to the MFP 100 by UserB and given the job name “DDD.txt” is“successful” (OK). Thus, the user can select a job with the storageresult 1702 that is “successful” (OK) and give an instruction to executethe job. With regard to a job with the storage result 1702 that is“unsuccessful” (NG), the user may change the settings of the job and thelike, and then input the job again from the PC 101 to the MFP 100. Theprocess illustrated in FIG. 16 ends after the process of step S1603.

The foregoing describes in detail the process for displaying the jobhistory in the MFP 100 according to the third exemplary embodiment.While the foregoing describes the exemplary case where “OK” is displayedto indicate that the received job has been successfully stored, and “NG”is displayed to indicate that the received job has not been successfullystored on the job list screen 1700 in FIG. 17, this is not a limitingcase. For example, a pop-up screen (not illustrated) from which the usercan easily understand that the job has been successfully stored or notsuccessfully stored may be displayed on the job list screen 1700 tonotify the user of the storage result. Alternatively, other identifiablemarks, sound, or light may be used to notify the user of the storageresult. Further, a notification of detailed information (e.g., reason ofunsuccessful storage of the job, etc.) about the job that was notsuccessfully stored at the time of receipt may also be provided as thestorage result.

As described above, in the third exemplary embodiment, the storageunsuccessful information (NG) is registered in the job history table1500 in the case where a job associated with user information has beenreceived and the received job has not been successfully stored. On theother hand, the storage successful information (OK) is registered in thejob history table 1500 in the case where the received job has beensuccessfully stored.

Then, when the job history is displayed, the user is notified of the jobthat has not been successfully stored and the job that has beensuccessfully stored such that each of the jobs is associated with userinformation. In this way, the user can easily recognize the jobs thatwere not successfully stored and the jobs that were successfully stored,among the jobs input by the user. This significantly improves userconvenience.

The foregoing exemplary embodiments are not seen to be limiting, and canbe modified in various ways (including organic combinations of theexemplary embodiments), wherein such modifications are not excluded fromthe scope of the present disclosure.

For example, while the various types of controls described above areperformed by the CPU 111 of the controller unit 110 of the MFP 100 inthe present exemplary embodiment, a part or all of the various types ofcontrols may be configured to be executable by a print control apparatussuch as an external controller that is in a different housing from theMFP 100.

Further, for example, while the present exemplary embodiments describethe case where print data of a received job and bibliographicinformation about the job are stored in the HDD 160 and the job isexecuted by a single MFP 100, this is not a limiting case. In a casewhere multiple MFPs 100 are communicably connected together via anetwork such as the LAN 102, a storage apparatus for storing print dataof a received job and a bibliography server apparatus for registering(storing) bibliographic information about the job may be included. Inthis case, a CPU 111 of another MFP 100 (output apparatus) may beconfigured to execute a job by requesting acquisition of print datastored in the storage apparatus and bibliographic information stored inthe bibliography server apparatus.

While various examples and exemplary embodiments of the invention aredescribed above, it is to be understood that the spirit and scope of thepresent disclosure are not limited to a specific description in thespecification.

Additional embodiments of the present invention can also be realized bya computer of a system or apparatus that reads out and executes computerexecutable instructions recorded on a storage medium (e.g.,computer-readable storage medium) to perform the functions of one ormore of the above-described embodiment(s), and by a method performed bythe computer of the system or apparatus by, for example, reading out andexecuting the computer executable instructions from the storage mediumto perform the functions of one or more of the above-describedembodiment(s). The computer may comprise one or more of a centralprocessing unit (CPU), micro processing unit (MPU), or other circuitry,and may include a network of separate computers or separate computerprocessors. The computer executable instructions may be provided to thecomputer, for example, from a network or the storage medium. The storagemedium may include, for example, one or more of a hard disk, arandom-access memory (RAM), a read only memory (ROM), a storage ofdistributed computing systems, an optical disk (such as a compact disc(CD), digital versatile disc (DVD), or Blu-ray Disc (BD)™), a flashmemory device, a memory card, and the like.

While the present disclosure has been described with reference toexemplary embodiments, it is to be understood that these exemplaryembodiments are not seen to be limiting. The scope of the followingclaims is to be accorded the broadest interpretation so as to encompassall such modifications and equivalent structures and functions.

This application claims the benefit of Japanese Patent Application No.2014-084719 filed, Apr. 16, 2014, which is hereby incorporated byreference herein in its entirety.

What is claimed is:
 1. A job processing apparatus comprising: a firststoring unit configured to store a job such that the job is associatedwith a user; a second storing unit configured to store identificationinformation for identifying the user associated with a job that has notbeen successfully stored in the first storing unit; and a notificationunit configured to notify the user that the job has not been storedaccording to login to the job processing apparatus, by the user, in acase where identification information for identifying the user havinglogged in to the job processing apparatus has been stored in the secondstoring unit.
 2. The job processing apparatus according to claim 1,further comprising a determining unit configured to determine whetherthe job has been successfully stored in the first storing unit, whereinaccording to the determination, by the determining unit, determines thatthe job has not been successfully stored, the second storing unit storesthe identification information for identifying the user associated withthe job that has not been successfully stored.
 3. The job processingapparatus according to claim 1, further comprising a deleting unitconfigured to delete the identification information stored in the secondstoring unit after a notification by the notification unit.
 4. The jobprocessing apparatus according to claim 3, wherein the deleting unitdeletes the identification information stored in the second storing unitaccording to execution of the job stored in the first storing unit isexecuted after a notification by the notification unit.
 5. The jobprocessing apparatus according to claim 3, wherein the deleting unitdeletes the identification information stored in the second storing unitaccording to logout from the job processing apparatus, by the user,after a notification by the notification unit.
 6. The job processingapparatus according to claim 3, wherein the deleting unit deletes theidentification information stored in the second storing unit accordingto elapse of a predetermined time after a notification by thenotification unit.
 7. The job processing apparatus according to claim 1,further comprising a display unit configured to display on a screen thejob stored in the first storing unit such that the job is associatedwith the user having logged in to the job processing apparatus, wherein,a notification from the notification unit is displayed on the screen. 8.The job processing apparatus according to claim 1, further comprising anauthentication unit configured to authenticate a user logging in to thejob processing apparatus.
 9. The job processing apparatus according toclaim 1, wherein the notification unit uses a message, mark, sound, orlight to notify the user that the job has not been stored.
 10. The jobprocessing apparatus according to claim 1, wherein the identificationinformation is a user name.
 11. A job processing system comprising: afirst job processing apparatus; and a second job processing apparatus,wherein the first job processing apparatus comprises: a first storingunit configured to store a job such that the job is associated with auser; a second storing unit configured to store identificationinformation for identifying the user associated with a job that has notbeen successfully stored in the first storing unit; and a sending unitconfigured to send the identification information stored in the secondstoring unit to the second job processing apparatus, and wherein thesecond job processing apparatus comprises: a receiving unit configuredto receive the identification information; and a notification unitconfigured to notify the user that the job has not been stored accordingto login to the second job processing apparatus, by the user, in a casewhere the identification information received by the receiving unitcontains identification information for identifying the user havinglogged in to the second job processing apparatus.
 12. A job processingapparatus comprising: a receiving unit configured to receiveidentification information for identifying a user that has been sentfrom another job processing apparatus different from the job processingapparatus in a case where a job has not been successfully stored suchthat the job is associated with the user in the another job processingapparatus; and a notification unit configured to notify the user thatthe job has not been stored according to login to the job processingapparatus, by the user, in a case where the identification informationreceived by the receiving unit contains identification information foridentifying the user having logged in to the job processing apparatus.13. A job processing apparatus comprising: a first storing unitconfigured to store a job such that the job is associated with a user; asecond storing unit configured to store identification information foridentifying the user associated with a job that has not beensuccessfully stored in the first storing unit; and a sending unitconfigured to send the identification information stored in the secondstoring unit to another job processing apparatus different from the jobprocessing apparatus.
 14. A control method in a job processingapparatus, the control method comprising: storing a job such that thejob is associated with a user; storing identification information foridentifying the user associated with a job that has not beensuccessfully stored; and notifying the user that the job has not beenstored according to login to the job processing apparatus, by the user,in a case where identification information for identifying the userhaving logged in to the job processing apparatus has been stored.
 15. Acomputer readable storage medium for storing computer executableinstructions for executing a method for controlling a job processingapparatus, the method comprising: storing a job such that the job isassociated with a user; storing identification information foridentifying the user associated with a job that has not beensuccessfully stored; and notifying the user that the job has not beenstored according to login to the job processing apparatus, by the user,in a case where identification information for identifying the userhaving logged in to the job processing apparatus has been stored in thestoring unit.